Resource search operations

ABSTRACT

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for identifying query-relevant content in a resource identified by a search result in response to the query. In one aspect, a method includes identifying resource search tidbits for a resource, each resource search tidbit being eligible for a resource search operation for the resource. The resource search tidbits are provided with search results to a client device. In response to a user selecting a resource identified by a search result, the client device identifies text in the resource matching the query-relevant text of the resource search tidbit and performs a resource search operation on the resource if the identified text meets a search operation threshold condition.

CLAIM OF PRIORITY

This application claims priority under 35 USC §119(e) to U.S. patentapplication Ser. No. 61/267,681, filed on Dec. 8, 2009, the entiredisclosure of which is hereby incorporated by reference.

BACKGROUND

This specification relates to digital information retrieval, andparticularly to processing search results to facilitate searchoperations.

The Internet provides access to a wide variety of resources, forexample, video files, image files, audio files, or Web pages includingcontent for particular subjects, book articles, or news articles. Asearch system can select one or more resources in response to receivinga search query. A search query is data that a user submits to a searchengine to satisfy the user's informational needs. The search systemselects and scores resources based on their relevance to the searchquery and on their importance relative to other resources to providesearch results that link to the selected resources. The search resultsare typically ordered according to the scores, and provided in a searchresults page.

The search results page displays a list of search results, and eachsearch result includes several lines of text (a “snippet”) that areintended to show how the page is relevant to the query. When a userclicks on a search result, the user's client device requests theresource—typically a web page—that the search result references. Whenthe page is received at the client device, however, the user may have tomanually search the page to find the relevant content, even if thesnippet included the exact content they want. The users often musteither scroll through the page to find the relevant content, or performa manual word search operation by use of a browser word search tool.

SUMMARY

In general, one innovative aspect of the subject matter described inthis specification can be embodied in methods that include the actionsof receiving a query, the query including one or more query terms;receiving, for each of a plurality of resources identified as beingrelevant to the query, one or more tidbits, each tidbit beingquery-relevant text extracted from the resource; for each tidbitextracted from each resource: determining whether the tidbit is eligiblefor a resource search operation that occurs in response to the resourcebeing rendered on a client device, and in response to determining thatthe tidbit is eligible for a resource search operation, marking thetidbit as being a resource search tidbit; and providing, for each of theplurality of resources, a corresponding search result responsive to thequery, each search result including a resource locator that specifiesthe location of the resource, and wherein at least one search resultincludes a resource search tidbit. Other embodiments of this aspectinclude corresponding systems, apparatus, and computer programs,configured to perform the actions of the methods, encoded on computerstorage devices.

Another aspect of the subject matter described in this specification canbe embodied in methods that include the actions of receiving, inresponse to a query including one or more query terms, a search resultspage including search results responsive to the query, each searchresult including a resource locator that specifies the location of aresource identified as being relevant to the query, and wherein at leastone search result includes a resource search tidbit, the resource searchtidbit being query-relevant text extracted from the resource andeligible for a research search operation in response to the resourcespecified by the resource locator of the at least one search resultbeing rendered on the client device; receiving a selection of the atleast one search result at the client device; receiving, in response tothe selection, the resource specified by the resource locator of the atleast one search result; rendering the resource at the client device;identifying a portion of text in the resource that matches thequery-relevant text of the resource search tidbit; and performing theresource search operation only if the identified portion of the textmatching the query-relevant text of the resource search tidbit meets asearch operation threshold condition. Other embodiments of this aspectinclude corresponding systems, apparatus, and computer programs,configured to perform the actions of the methods, encoded on computerstorage devices.

The details of one or more embodiments of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter will become apparent from the description, the drawings,and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a search system that facilitates resourcesearch operations on a client device.

FIG. 2 is a block diagram of an example process flow for identifyingresource search tidbits in a tidbit processor.

FIGS. 3A-3C are Venn diagrams illustrating an example eligibility rulefor determining whether a tidbit is eligible for a resource searchoperation.

FIG. 4 is a flow diagram of an example process for identifying resourcesearch tidbits.

FIG. 5 is a flow diagram of an example process for determining whether atidbit for a resource is eligible for a resource search operation.

FIG. 6 is a block diagram of an example process for associating resourcesearch tidbits with resource locators from a search results page.

FIG. 7A is an illustration of an example rendering of a resource forwhich a portion of text matching the query-relevant text of the resourcesearch tidbit does not meet a search operation threshold condition.

FIG. 7B is an illustration of an example rendering of a resource forwhich a portion of text matching the query-relevant text of the resourcesearch tidbit does meet a search operation threshold condition.

FIG. 8 is a flow diagram of an example process for performing a resourcesearch operation.

FIG. 9 is a flow diagram of an example process for determining whether aportion of text in a resource matches the query-relevant text of aresource search tidbit.

FIG. 10 is a flow diagram of an example process for navigating to aportion of a resource in response to selecting a resource search tidbit.

FIG. 11 is a flow diagram of performing a resource search operationusing an association of resource locators and resource search tidbits.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a search environment 100 that facilitatesresource search operations on a client device. The example environment100 includes a network 102, e.g., a local area network (LAN), wide areanetwork (WAN), the Internet, or a combination of them. The network 102connects Websites 104, client devices 106, and the search system 110.The environment 100 may include many thousands of publishers 104 andclient devices 106.

A Website 104 is one or more resources 105 associated with a domain nameand hosted by one or more servers. An example Website is a collection ofWeb pages formatted in hypertext markup language (HTML) that can containtext, images, multimedia content, and programming elements, e.g.,scripts. Each Website 104 is maintained by a publisher, e.g., an entitythat manages and/or owns the Website.

A resource 105 is any data that can be provided by a Website 104 overthe network 102 and that is associated with a resource address.Resources 105 include HTML pages, word processing documents, andportable document format (PDF) documents, images, video, and feedsources, to name just a few. The resources 105 can include content,e.g., words, phrases, images and sounds and may include embeddedinformation (e.g., meta information and hyperlinks) and/or embeddedinstructions (e.g., JavaScript scripts).

A client device 106 is an electronic device that is under control of auser and is capable of requesting and receiving resources 105 over thenetwork 102. Example client devices 106 include personal computers,mobile communication devices, and other devices that can send andreceive data over the network 102. A client device 106 typicallyincludes a user application, e.g., a web browser, to facilitate thesending and receiving of data over the network 102.

To facilitate searching of resources 105, the search system 110identifies the resources 105 by crawling and indexing the resources 105provided on Websites 104. Data about the resources 105 can be indexedbased on the resource to which the data corresponds. The indexed and,optionally, cached copies of the resources 105 are stored in an indexedcache 112.

The client devices 106 submit search queries 109 to the search system110. For instance, any particular search query 109 can include one ormore terms consisting of words, numbers or other characters. As anexample, the search query 109 entered by the user can be “pachinko 1975Japan” to search online for information regarding the Japanese uprightpinball games. In response, the search system 110 accesses (e.g., usinga search engine) the indexed cache 112 to identify resources 105 thatare relevant to the search query 109. The search system 110 identifiesthe resources 105, generates search results 111 that identify theresources 105, and returns the search results 111 to the client devices106. For example, the search results 111 can include resources 105corresponding to Web hits related to “1975 Japanese pachinkos” inresponse to the user's search query 109. A search result 111 is datagenerated by the search system 110 that identifies a resource 105 thatis responsive to a particular search query, and includes a link to theresource 105. An example search result 111 can include a Web page title,a snippet of text or a portion of an image extracted from the Web page,and the URL of the Web page.

For a search of textual content, the search results are ranked based onscores related to the resources 105 identified by the search results111, such as information retrieval (“IR”) scores, and optionally aquality score of each resource relative to other resources. In someimplementations, the IR scores are computed from dot products of featurevectors corresponding to a search query 109 and a resource 105, and theranking of the search results is based on initial relevance scores thatare a combination of the IR scores and page quality scores. The searchresults 111 are ordered according to these initial relevance scores andprovided to the client device 106 according to the order.

The client devices 106 receive the search results 111, e.g., in the formof one or more search result pages 126, and render the search results111 for presentation to users. In response to the user selecting a linkin a search result 111 at a client device 106, the client device 106requests the resource 105 identified by the link. The Website 104hosting the resource 105 receives the request for the resource 105 fromthe client device 106 and provides the resource 105 to the requestingclient device 106.

The search results 111 include the identification of resources 105 thatare relevant to the user's search, such as a set of query terms enteredby the user into a Web browser on the client device 106. When theresources 105 are identified as relevant to the user's search, thesearch system 110 identifies one or more tidbits and selects a subset ofthe tidbits for potential inclusion as a snippet. As used herein, a“tidbit” is query-relevant text that can be included in a snippet. A“snippet” can include one or more tidbits. Each snippet can includequery-relevant text extracted from the resource 105 specified by theresource locator (e.g., the resource's URL) of the search result.Snippets can be rendered on the client device 106 as part of the searchresult. In some implementations, a tidbit is a portion of contiguoustext in the resource, such as a group of adjacent words in the searchresult 111 displayed on the user's client device 106. The search results111 can also include one or more snippets, each including one or moretidbits.

The search system 110 can provide the query, the resources (or dataidentifying the resources) and the tidbits for each of the resources toa tidbit processor 113. The tidbit processor 113, which is described inmore detail in FIG. 2, determines for each tidbit whether the tidbit iseligible for a resource search operation that occurs in response to theresource being rendered on a client device 106. In response todetermining that a particular tidbit is eligible for a resource searchoperation, the tidbit processor 113 marks the tidbit as a resourcesearch tidbit (RST). The use of resource search tidbits is described inmore detail below. For each resource, the tidbit processor 113 informsthe search system 110 of the identified resource search tidbits, if any.

Once a search results page 126 is presented to the user, displaying thesearch results 111, the user can make a selection. For example, the usercan review the search results 111, including examining the snippetsdisplayed for each resource 105 corresponding to each individual searchresult 111. Upon seeing a particular search result of interest, forexample, the user can click the URL or other resource locator for theresource 105 to display a page 128 corresponding to the resource 105.The page 128 can be, for example, the rendered resource 105corresponding to the news story, product review, home page,advertisement, or any other Web page selected by the user from thesearch results 111. If the information on the page 128 is textual, forexample, and does not fit entirely within the viewport of the clientdevice 106, one or more scroll bars 130 within the user interface of theclient device 106 can be used to manage the display of the page 128.Upon initial navigation to a page 128, because the first few or “top”paragraphs or sections of the Web site's information are displayed, thescroll bar 130 is scrolled to the top.

Sections of the Web site of most interest to the user (e.g., the Webcontent portions that correspond to query-relevant tidbits) may notappear in the top, or immediately viewable, portion of the Web page. Inother words, the information does not fit entirely within the viewportof the client device 106, or is difficult for the user to find on thescreen.

To provide more convenient and faster access to the sections ofinterest, a selection environment 132 is displayed. The selectionenvironment displays resource search tidbits 134 for the resource, eachcontaining a portion of the query-relevant text of the resource. Forexample, the selection environment 132 can include one or more resourcesearch tidbits 134 corresponding to text in the resource that matchesthe user's search terms (e.g., “pachinko 1975 Japan”). The sections oftext of most closely matching the user's search terms may be embedded ina portion of the resource 105 that is not initially displayed on theclient device 106. Using the selection environment 132, the user canquickly identify and navigate to those corresponding passages of theresource 105. For example, as depicted in FIG. 1, the selectionenvironment 132 includes three user-selectable lines, each a resourcesearch tidbit, the second of which is highlighted to indicate selectionby the user.

One advantage of the selection environment 132 is to overcome theproblem of limited viewports, such as the viewport on the client device106. Depending on the web page being displayed and the client device106, the resource 105 may not be visible to a user of the device becausethe resource 105 contains too much information to fit entirely withinthe device's viewport. For example, because of the zoom level of theviewport (e.g., the viewport is zoomed-in), the size of the viewportand/or the dimensions of the web page, not all of the web page'scontents can be displayed in the viewport at the same time. For mobiledevices, displaying a web page such a scenario is a common occurrencebecause of the mobile device's relatively small viewport.

The query-relevant text of a resource search tidbit included in thesearch result can be, in some implementations, a subset of thequery-relevant text of the snippet included in the search result. Insome implementations, the resource search tidbits are tidbits that neednot necessarily be part of the snippet of the search result, meaningthat they are not rendered on the client device 106 as part of thesearch results 111.

Upon selection of a particular resource search tidbit 134 (e.g., thesecond of three) from the selection environment 132, the state ofinformation displayed in the page 128 can change, as indicated by thearrow 136. In the newly-displayed state of the page 128, the resource105 has scrolled to the section of page that corresponds to the resourcesearch tidbit selected by the user. Moreover, the query-relevant text138 associated with the user-selected resource search tidbit 134 isshown highlighted (e.g., highlighted in FIG. 1 by using a box around thetext). For example, while the resource 105 may describe “Japan” ingeneral, the query-relevant text that is of interest to the user can beembedded much further down in the document and made more easilylocatable using the user-selectable resource search tidbits 134 that areincluded in the selection environment 132.

Highlighting of query-relevant text can be accomplished using coloredhighlighting behind the text. In some implementations, “highlighting”can be accomplished by bolding the text, using a different font family,using a different text color, or by various combinations thereof.

FIG. 2 is a block diagram of an example process flow 200 for identifyingresource search tidbits 202 in the tidbit processor 114. The tidbitprocessor 113 can be implemented as a component of the search system110, or can be a separate system in data communication with the searchsystem 110. The resource search tidbits 202 identified by the tidbitprocessor 113 are called “resource search tidbits.” Resource searchtidbits are tidbits that are eligible to be used on a client device 106to search a resource for query-relevant text corresponding to thetidbits as part of a resource search operation. The resource searchoperations, which is described in more detail below, occurs in responseto selecting a search result that identifies the resource.

The tidbit processor 113 receives as input the query 109, a resource URL206 for each resource identified as being relevant to the query 109, oneor more tidbits 208 (e.g., tidbit₁ through tidbit_(n)) extracted thatthe search system 110 has identified as including query-relevant text,and a resource 105 identified by the URL 206 and from which the tidbits208 are extracted. Depending on these inputs and relationships amongthem (e.g., comparisons of tidbits with terms in the URL, query termswithin the query 109, and portions of titles within the resource 105),the tidbit processor 113 can identify resource search tidbits (RSTs) 202in addition to the URLs provided to the client device 106 for renderingthe resources.

The query 109 can include the one or more user-defined query terms, suchas words, numbers, etc. that are input into the search query field of aWeb browser executing on the user's client device 106. In someimplementations, the search system 110 can generate one or more tidbits208 that correspond to each resource 105 identified as being responsiveto the query 109. Based on the other inputs it receives, the tidbitprocessor 113 can reduce the list of candidate tidbits 208 to just thosetidbits 208 that are appropriate for use as resource search tidbits(RSTs) 202. For example, while several (e.g., several dozen) tidbitsrelated to 1975 Japanese pachinkos can be identified by the searchsystem 110 in response to the query “pachinko 1975 Japan” and providedto the tidbit processor 113, only a handful (e.g., one to ten) mayultimately end up being used to generate resource search tidbits (RSTs)202. Specifically, the candidate tidbits not used for resource searchtidbits (RSTs) 202 can be those eliminated from consideration (e.g.,using eligibility rules) by the tidbit processor 113 when comparing thetidbits 208 to the query 109, the URL 206, and the resource 105.

FIGS. 3A-3C are Venn diagrams illustrating an example eligibility rulefor determining whether a tidbit is eligible for a resource searchoperation. The example Venn regions include a resource region and atidbit region. The resource region is representative of one or morefeatures associated with a resource and the terms that are included inthose features. Example features associated with the resource includethe URL of the resource, the title of the resource, and even theresource itself. The tidbit region is representative of the terms in thetidbit. In some implementations of using tidbit eligibility rules, if aparticular tidbit includes at least one query term that is not includedin the title of the resource, then the tidbit can be used as a resourcesearch tidbit (RST). In other implementations, if a particular tidbitincludes at least one query term that is not included in the title ofthe resource or in the resource locator (e.g., URL) of the resource,then the tidbit can be used as a resource search tidbit (RST). Othereligibility rules can also be used, such as rules that take into accountthe display formatting of query terms in the resource, etc.

In some implementations, rules can also be based on the use of wordvariants, synonyms, or edit distances. For example, word variants (orwords based on word stems) such as “features” and “featured” can triggera match condition. Synonym matching, when used in tidbit eligibilityrules, can include synonym pairs such as “Eisenhower” and “Ike,” “BillClinton” and “President Clinton,” or “green” and “environmental.” Insome implementations, synonym matching can depend on the context (e.g.,other text in the resource), such as to avoid false matches, forexample, of the color green versus the “green” (environmental) movement.Edit distances can measure, for example, the relative number ofindividual character edits required to change Word A into Word B, and ina sense can be similar to word stemming.

Referring to FIG. 3A, Venn diagram 300 illustrates the use of an exampleeligibility rule that results in the selection of a resource searchtidbit_(j) (RST_(j)) 302. In this example, a resource region 304 withinthe Venn diagram includes query terms 1, 2 and 3, meaning that the queryterms 1, 2 and 3 are included in the one or more features represented bythe region 304, e.g., the resource's title, URL or both. A tidbit_(j)region 306 includes query terms 3 and 4, meaning that the query terms 3and 4 are included in the tidbit_(j). The overlap of the regions 304 and306 is indicated by the intersection 308 that includes the query term 3that occurs both in the resource feature(s) (e.g., the title and/or URL)and in the tidbit_(j). In this example, because at least one query term(e.g., the query term 4) is not included in the resource, the tidbit isdeemed eligible for being a resource search tidbit (e.g., the RST_(j)302).

Referring to FIG. 3B, Venn diagram 310 illustrates the use of an exampleeligibility rule that results in the selection of a resource searchtidbit_(k) (RST_(k)) 312. In this example, a resource region 314 withinthe Venn diagram includes query terms 1 and 2, meaning that the queryterms 1 and 2 are included in the one or more features represented bythe region 304, e.g., the resource's title, URL or both. A tidbit_(k)region 316 includes query term 3, meaning that the query term 3 isincluded in the tidbit_(k). The overlap of the regions 314 and 316 isthe region 314 itself, as query terms 1 and 2 occur both in the resourcefeature(s) (e.g., the resource's title and/or URL) and in thetidbit_(k). In this example, because at least one query term (e.g., thequery term 3) is not included in the resource, the tidbit is deemedeligible for being a resource search tidbit (e.g., the RST_(k) 312).

Referring to FIG. 3C, Venn diagram 320 illustrates the use of an exampleeligibility rule that results in not selecting a resource searchtidbit_(m) (RST_(m)) 322. In this example, a resource region 324 withinthe Venn diagram includes query terms 1, 2, 3 and 4, meaning that thequery terms 1, 2, 3 and 4 are included in the features represented bythe region 304, e.g., the resource's title, URL or both. A tidbit_(m)region 326 includes query terms 3 and 4, meaning that the query terms 3and 4 are included in the tidbit_(m). The overlap of the regions 314 and316 is the region 314 itself, as query terms 3 and 4 occur both in theresource feature(s) (e.g., the title and/or URL) and in the tidbit_(m).However, in this example, because no query terms included in thetidbit_(m) are absent from the resource feature(s), the tidbit is noteligible for being a resource search tidbit (e.g., the RST_(m) 322). Asa result, the tidbit fails to meet eligibility requirements, forexample, for being included in the selection environment 132 describedwith reference to FIG. 1. In some implementations, determining whether atidbit is eligible for a resource search operation can result when allof the query terms are included in the tidbit.

FIG. 4 is a flow diagram of an example process 400 for identifyingresource search tidbits. The tidbit processor 113, for example, canperform the steps of the process 400.

A query that includes one or more query terms is received (402). As anexample, the tidbit processor 113 can receive the query 109, which canoriginate from the client device 106. For example, a user can enter thequery terms (e.g., “pachinko 1975 Japan”) of the query 109 in a searchbox of a Web browser or other user application.

For each of a plurality of resources identified as being relevant to thequery, one or more tidbits are received, each tidbit beingquery-relevant text extracted from the resource (404). As an example,the tidbit processor 113 can receive the tidbits 208 from the searchsystem 110, which can automatically send one or more tidbits with anyresource that is responsive to the query processed by the search system110. If the query 109, for example, is “pachinko 1975 Japan,” then thetidbits 208 can be query-relevant text extracted from resources 105(e.g., Web pages) that correspond to the query 109 entered by the useron the client device 106. For instance, example tidbits 208 can include“in 1975, tens of thousands of Japanese pachinkos were replaced . . . ”or “Japan sent boatloads of reconditioned pachinkos to the US in 1975,”to name a few examples.

The tidbit from the resource is examined (406). Examination can include,for example, text in the tidbit 208 to determine if query terms withinthe tidbit 208 are contained in the title of the resource 105 and/orembedded within the resource's resource locator (e.g., the resource'sURL).

A determination is made whether the tidbit is eligible for a resourcesearch operation (408). For instance, the tidbit processor 113determines a tidbit 208 to be eligible for a resource search operationif, for example, at least one query term in the tidbit 208 is notcontained in the resource 105 title and/or URL.

If the tidbit is eligible for a resource search operation, then thetidbit is marked as being a resource search tidbit (410). For example,the tidbit 208 (e.g., “in 1975, tens of thousands of Japanese pachinkoswere replaced . . . ”) is marked as a resource search tidbit. As shownin FIG. 2, the “marking” can occur when the tidbit processor 113 outputsor otherwise identifies the tidbit 208 as a resource search tidbit (RST)202.

A determination is made whether more resources and tidbits remain to beprocessed (412). For instance, the tidbit processor 113 can processmultiple tidbits 208 for each or multiple resources 105.

In some implementations, when the search system 110 identifies asignificant number of resources 105 in response to the query 109, thetidbits 208 provided by the search system 110 can be limited initiallyto only those tidbits 208 that correspond to a subset of the resources,such as only those resources on the first page of search results. Later,if the user begins reviewing search results on a subsequent page, thesearch system 110 can provide tidbits 208 for additional resources 105,as needed.

For each of the plurality of resources, a corresponding search resultresponsive to the query is provided, with at least one search resultincluding a resource search tidbit (414). At least one search resultincludes a resource search tidbit when at least one resource searchtidbit is identified as being eligible for a resource search operation.For example, for each resource 105, the search system 110 can provide asearch result 109. If the resource search tidbit 202 is, for example,part of the snippet of the search result, the resource search tidbit canbe marked by use of HTML <span> tags. Other ways of marking a resourcesearch tidbit can also be used.

FIG. 5 is a flow diagram of an example process 500 for determiningwhether a tidbit for a resource is eligible for a resource searchoperation. The tidbit processor 113, for example, can perform the stepsof the process 500.

Query terms in a resource region are identified (502). The resourceregion can include the resource itself, and/or specific portions of theresource, and/or the URL of the resource, and/or other features of theresource. For example, a resource 105 related to pachinkos can includeone or more titles and subtitles within the text of the resource, andcan be identified by a corresponding URL. Individual query terms fromthe user's query 109 can be identified in the title section, and/or theURL of the resource.

Query terms in the tidbit are identified (504). In some implementations,the query terms identified in the tidbit (e.g., one of the tidbits 208)can already have been tagged by the search system 110. If not, the queryterms in the tidbit can be identified with reference to those queryterms in the query 109.

Query terms in the tidbit are compared to query terms in the resourceregion (506). In some implementations, synonyms can be used to matchquery terms to the title section, such as “Ike” (e.g., as a query term)for “Eisenhower” (e.g., as a word in the title section) to name oneexample. Other term matching techniques can use word stems, such as tomatch “Japan” with “Japanese” or “featured” with “features” to name afew examples. In some implementations, query terms can also be comparedto the resource locator (e.g., URL).

A determination is made whether at least one query term exists in thetidbit that is not in the resource region (508). For example, in someimplementations of using eligibility rules for generating resourcesearch tidbits (RSTs) 202, an RST will not be created unless at leastone query term (e.g., from the query 109) is absent from thecorresponding resource 105. Specifically, an RST 202 is eligible to becreated if the tidbit 208 includes at least one query term that is notin the title section or the resource locator (e.g., URL) of the resource105. In the current example, an RST 202 can be created by the tidbitprocessor 113 if a pachinko-related resource does not “include” all of“pachinko 1975 Japan” somewhere in the resource's title section and/orURL. Again, in some implementations, “including” can include query termmatching using synonyms, word stemming and edit distances.

If at least one query term exists in the tidbit that is not in theresource region, then the tidbit is marked as being eligible as aresource search tidbit (510). For example, the tidbit processor 113,after comparing one of the tidbits 208 with the title section of theresource 105, can output the tidbit 208 as a resource search tidbit(RST) 202. Generation of the RST 208 can include the tidbit itself plusany additional information needed to place the RST 208 in the selectionenvironment 132 and to enable ultimate selection of the RST 208 by theuser and navigation to the corresponding query-relevant text portion inthe resource 105.

A determination is made whether more tidbits for the current resourceremain to be processed (512). For example, a resource 105 can have morethan one tidbit 208 provided for it, and the tidbit processor 113 canprocess all of the tidbits for the resource to determine which tidbits208, if any, are candidates for becoming eligible for becoming resourcesearch tidbits (RSTs) 202.

In some implementations, the tidbit processor 113 can stop processingtidbits 208 for a resource 105 when a threshold number (e.g., five RSTs202) have been identified, so as not to overwhelm the user with too manyRSTs 202 in a selection environment of a resource search operation. Insome implementations, all tidbits 208 for a resource 105 can beprocessed by the tidbit processor 113, and the best RSTs 202 can beprovided to the user, discarding, for example, RSTs 202 of lower qualityas determined by a ranking algorithm. In some implementations, thetidbit processor 113 can generate at least one RST 113 even if not allof the query terms are exact matches to query-relevant text within theresource 105 in order to have at least one RST 113 that the user canuse.

If more tidbits for the current resource remain to be processed, thenthe next tidbit is obtained (514). Processing the next tidbit can resumeat step (504) of the process 500. For example, query terms in the tidbitare identified (504), and so on for the next tidbit and for each tidbitprocessed.

A determination is made whether more resources remain to be processed(516). For example, in response to the query 109, the search system 110can provide multiple resources 105. The tidbit processor 113 can processeach of the resources 105 and their tidbits 208 in order to determineRSTs 202.

If more resources remain to be processed, then the next resource isobtained (518), and processing the next resource can resume at step(502) of the process 500. When all resources 105 have been processed bythe tidbit processor 113, the process 500 ends (520).

FIG. 6 is a block diagram of an example process for associating resourcesearch tidbits with resource locators from a search results page. Anexample search results page 602 lists search results 608 a-608 c thatcorrespond to a search query 604. For example, a user running a Webbrowser on the client device 106 can enter the search query 604 (e.g.,“new widget features”) in order to access Internet information relatedto widgets having new features. The client device 106 can send the query109 (e.g., including query terms from the user's search query 604) overthe network 102, where it can be handled by a search system 110. Inresponse to the query 109, the search system 110 can return the searchresults 111.

On the search results page 602, the search results 111 can be displayedas the individual search results 608 a-608 c. These search results 608a-608 c correspond to the resources 105 described with reference toFIG. 1. In the search result 608 a, a resource title 610 a (e.g.,“Product Review for Widget”) provides a title-level description of thesearch result 608 a. In this case, the resource title 610 a alsoincludes one of the query terms of the search query 604, namely“Widget.” The search result 608 a also includes a snippet 612 a of

“Our new widget has new features . . . If you desire a new full-featuredwidget . . . . ” in which the query terms, or likenesses thereof, arebolded. For example, the likenesses of the query terms of the searchquery 604 can include synonyms, word stems or variants (e.g.,“full-featured”), and words within a threshold edit distance. The searchresult 608 a further includes a resource locator 614 a, in this case theURL “www.example11.com/business/widget.php?p=93” that can be used toaccess the resource 105. As an example, the user can click on the URL tonavigate to the web page associated with the resource locator 614 a.

The other search results on the search results page 602, namely thesearch results 608 b and 608 c each have their respective titles 610 band 610 c, snippets 612 b and 612 c, and resource locators 614 b and 614c. Within the snippets 612 b and 612 c, terms in the snippets that“match” the query terms of the search query 604 are also bolded. In someimplementations, words in titles, snippets and resource locators can behighlighted in various ways, such as with different colors ofhighlighting (e.g., a different color for each query term), shading,different font colors, different font families, bolding, italics, or anyother mechanism for providing a different visible look to the user. Insome implementations, hovering over, or clicking on, a query term cancause all instances of that query term to be highlighted in some way.

Resource search tidbit information 622, which identifies resource searchtidbits for each search result 608, is also provided with the searchresults page. The resource search tidbit information 622 need not bedisplayed as part of the page; instead, the information can be of theform of marked resource search tidbits for each search result. Forexample, a resource search tidbit can be query-relevant text that isindependent of the query-relevant text of a snippet for a search result,i.e., the resource search tidbit may be a block of text that is not partof the snippet.

For instance, the resource search tidbit information 622 can include,for each search result (e.g., search results 608 a -608 c), the searchresult's resource locator (e.g., URL) and associated resource searchtidbit. For the search result 608 a, the Web browser executing on theclient device 106 can process, in response to a selection of the searchresult 608 a, the two resource search tidbit (as indicated by “URL₁:RST₁₁, RST₁₂”) to determine whether a resource search operation is to beperformed.

In some implementations, the associations between resource searchtidbits and resource locators can be stored, for example, by processinga document object model (DOM) representation of the search results page.Web browser applications can use various internal representations of thedocument, such as a document object model (DOM) representation, formanaging and rendering documents to be displayed to the user. Any of therepresentations can be used, for example, to associate resource locators(e.g., URLs) with resource search tidbits (RSTs), such as will bedescribed with respect to the process flow diagram FIG. 11.

The Web browser's rendering module (e.g., part of the Web browserexecuting on the user's client device 106) can translate a displayedmarkup language document using some type of translation, such as to aDOM representation. The translation can analyze the internalrepresentation of the current document, extract text from the text nodesof the representation, and send the text to a browser translation modulefor translation. The page translator module can receive the translatedtext from the browser translator module and updates the internalrepresentation. The rendering component of the browser can then renderthe updated internal representation. In general, the term “web browser”when used herein can refer to any web browser application, any browserextension, or any other program running on the client (or server) thatfacilitates browsing online content.

The DOM representation of a document is in the form a tree of nodeobjects. Each node corresponds to a part of the document. Nodes can bevarious types including, for example, root nodes, element nodes,attribute nodes, text nodes and script nodes. A text node is a nodecorresponding to text in the document, and includes text stored in thenode. An element node is a node corresponding to an annotation in thedocument such as <html> tags or <title> tags. An attribute node is anode corresponding to an attribute of an element node, such as thesource for an <image> tag. A script node includes an executable script.A DOM representation can also include other types of nodes.

By traversing the DOM of the search results page, the browser identifiesthe resource search tidbits that have been marked for each URL andstores the association in memory. The association is then accessed eachtime a page is requested by a selection of a search result, and the webbrowser uses the association to determine which resource search tidbitsto search for in a given page. Using the resource search tidbits for thepage, the web browser determines whether the resource search tidbitsmeet a resource search operation threshold condition.

FIG. 7A is an illustration of an example rendering of a resource forwhich a portion of text matching the query-relevant text of the resourcesearch tidbit does not meet a search operation threshold condition. Therendering shows an example page 702. For instance, the page 702displayed represents an example Web Page that can be rendered if theuser selects the search result 608 a, as described with reference toFIG. 6. Both the Web page title 704 and the address 706 match theresource locator 614 a (e.g.,“www.example11.com/business/widget.php?p=93”). To obtain the resourceinformation needed to render the webpage 702, communication by theclient device 106 across the network 102 (e.g., an HTTP get) involvesrequesting the resource associated with the resource locator 614 a.

The page 702 can be rendered, for example, by a Web browser executing onthe user's client device 106. When the page 702 is rendered, the Webpage content 708 is displayed, including any graphics and textassociated with the resource. Query-relevant text may or may not behighlighted, and if so, the highlighted text passages 710 and 712correspond to the resource search tidbits (e.g., “RST₁₁ and RST₁₂”) thatare included in the resource search tidbit information 622 andcorrespond to the resource locator 614 a (e.g., the URL“www.example11.com/business/widget.php?p=93”). The Web browser on theclient device 106 can have the ability to highlight the query-relevanttext associated with the resource search tidbits if, for example, theassociations between the resource locator (e.g., the resource's URL) andthe resource search tidbits are accessible from document object models(DOMs) from the previous search results page stored in computer memory.In this example, the page 702 does not include a selection environment132 because, in this example, the query-relevant text associated withresource search tidbits (e.g., “RST₁₁ and RST₁₂”) are near enough to the“top” of the Web page content 708 (e.g., above the “fold”) so as not towarrant displaying a control that allows the user to quickly navigatesignificantly “lower” on the Web page.

FIG. 7B is an illustration of an example rendering of a resource forwhich a portion of text matching the query-relevant text of the resourcesearch tidbit does meet a search operation threshold condition. Therendering is of an example page 722. For instance, the page 722displayed represents an example Web Page that can be rendered if theuser selects the search result 608 c, as described with reference toFIG. 6. Specifically, both the Web page title 724 and the address 726match the resource locator 614 c (e.g.,“www.example1435.com/business/classicgadgets.html”). To obtain theresource information needed to render the webpage 722, communication bythe client device 106 across the network 102 (e.g., “Get URL₃”) involvesrequesting the resource associated with the resource locator 614 c.

The page 722 can be rendered, for example, by a Web browser executing onthe user's client device 106. When the page 722 is rendered, the Webpage content 728 is displayed, including any graphics and textassociated with the resource.

In this example, the text corresponding to the resource search tidbitsassociated with the resource are positioned sufficiently lower withinthe content of the Web page so as not to be displayed when the Web pageappears. Essentially, the text of the resource search tidbits arescrolled off the page. However, the browser executing on the clientdevice 106, for example, can recognize the rendered location of thequery-relevant text and automatically display a selection environment730. A best matches message 732 included in the selection environment730 can echo the query terms (e.g., “new widget features”) that areincluded in the user's original search query 604, as described withreference to FIG. 6. The selection environment 730 can further includethe resource search tidbits (e.g., “RST₃₁ and RST₃₂”) associated withthe query-relevant text passages, in this case selection environmentoptions 734 and 736. Specifically, the option 734 can be selected by theuser to navigate to the portion of the web content containing the text738 matching the resource search tidbit RST₃₁, and the option 736 tonavigate to the text 740 matching the resource search tidbit RST₃₂. Theoption 734 is depicted in FIG. 7B as containing the text “RST₃₂” inorder to make clear the mapping of the RST to its correspondingquery-relevant text in the resource. However, the option 736 includesthe tidbit “several of our new-featured widgets” which matches thequery-relevant passage 740. In some implementations, including the onedepicted in FIG. 7B, query terms that appear in tidbits andquery-relevant text can be highlighted in any way (e.g., shown hereusing bolding).

In this example depiction of the web page 722, the query-relevantpassages 738 and 740 are displayed in a phantom region 742 used here toindicate and extension of the web page 722 beyond the active viewport.

The query-relevant text is highlighted, and the text passages 710 and712 correspond to the resource search tidbits (e.g., “RST₃₁ and RST₃₂”)that are included in the resource search tidbit information 622 andcorrespond to the resource locator 614 a (e.g., the URL“www.example11.com/business/widget.php?p=93”). The Web browser on theclient device 106 has accesses associations between the resource locator(e.g., the resource's URL) and the resource search tidbits areaccessible from data gathered from document object model (DOM) andstored in computer memory.

FIG. 8 is a flow diagram of an example process 800 for performing aresource search operation. As an example, the client device 106(described with reference to FIG. 1) can perform the steps of theprocess 800. More specifically, the process 800 can be executed, forexample, by computer applications that are part of, our in communicationwith, Web browser applications or other Web search and content renderingapplications running on a user's client device 106.

In response to a query including one or more query terms, a searchresults page including search results responsive to the query isreceived (802). Each search result includes a resource locator thatspecifies the location of a resource identified as being relevant to thequery. At least one search result includes a resource search tidbit. Theresource search tidbit is query-relevant text extracted from theresource. The resource search tidbit is eligible for a research searchoperation in response to the resource specified by the resource locatorof the at least one search result being rendered on the client device.Referring to FIG. 1, for example, the search results page can be the webpage 126 that displays the search results 111 provided by the searchsystem 110. The search results 111 can include snippets from and linksto resources 105 that the search system 110 identifies as responsive tothe user's query 109. The search results 111 can be displayed orrendered within a graphical user interface on the screen of the user'sclient device 106. For example, if the user's query 109 is “pachinko1975 Japan,” then the search results page displayed as the web page 126can include Web or Internet “hits” related to the query. As result, theuser can see, within each of the search results 111, resource locators(e.g., links or URLs) for each resource 105, and snippets that cancontain some or all of the individual query terms from the query 109.

A selection of the at least one search result is received at the clientdevice (804). For example, from the search results 111 displayed on theuser's client device 106, the user can select one of the individualsearch results 111. Continuing with the current example, the user canselect a particular search result, such as a search result 111corresponding to the history of pachinko games in Japan. The user'sselection of the particular search result 111, for example, can causethe Web browser application to obtain the URL (or other resourcelocator) that is associated with or embedded within the search result111.

In response to the selection, the resource specified by the resourcelocator of the at least one search result is received (806). Forexample, using the URL of the selected search result 111, the Webbrowser application can access the corresponding resource 105. Accesscan occur, for example, over the network 102, using the URL of theresource 105.

The resource is rendered at the client device (808). As an example, theresource 105 can be displayed within the user's Web browser, such as todisplay the Web page that provides a history of pachinko games in Japan.

A portion of text in the resource that matches the query-relevant textof the resource search tidbit is identified (810). As an example,referring to FIG. 1, an application on the client device 106 identifiesquery-relevant text 138 corresponding to the specific resource searchtidbit 134.

The resource search operation is performed only if the identifiedportion of the text matching the query-relevant text of the resourcesearch tidbit meets a search operation threshold condition (812). Forexample, in some implementations, certain threshold conditions mustexist before the resource search operation is performed. Specifically,unless the query-relevant text 138 corresponding to a specific resourcesearch tidbit 134 appears below the “fold” (e.g., a pre-determinednumber of pixels from the top of the display or outside of the currentview port), the selection environment 132 is not displayed.

In some implementations, the selection environment 132 can display allresource search tidbits 134 no matter how many of the resource searchtidbits' corresponding query-relevant text passages appear above orbelow the fold. In other implementations, the selection environment 132displays only the resource search tidbits for which corresponding textpassages are below the fold.

FIG. 9 is a flow diagram of an example process 900 for determiningwhether a portion of text in a resource matches the query-relevant textof a resource search tidbit. As an example, the client device 106(described with reference to FIG. 1) can perform the steps of theprocess 900. More specifically, the process 900 can be executed, forexample, by computer applications that are part of, or in communicationwith, Web browser applications or other Web search and content renderingapplications running on a user's client device 106.

In some implementations, the resources that are processed by the searchsystem 110 are cached resources, and the resources may have been updatedby administrators or users after the resource is stored in a cache ofthe search system 110. Accordingly, the copy of the resource stored inthe cache of the search system 110 may not exactly match the copy of theresource that is provided by the website hosting the resource.Accordingly, the client device, in some implementations, is configuredto search for matching text based on an exact match and a closest matchcriteria.

A portion of text in the resource that exactly matches thequery-relevant text of the resource search tidbit is searched for (902).For example, a Web browser application running on the client device 106can search for query-relevant text in a resource 105 that matches all ofthe text in the resource search tidbit.

A determination is made whether an exact match is found (904). If anexact match is found, then the portion of text in the resource thatexactly matches the text of the resource search tidbit is identified(906). The identification can be used to highlight the text on some way,such as to highlight the query-relevant text 138 in the resource 105.The query-relevant text 138 in this case can contain all of the queryterms (e.g., all of the terms in “pachinko 1975 Japan”).

If no exact match is found, then the portion of text in the resourcethat most closely matches the text of the resource search tidbit isidentified (908). For example, in this case, the text identified in theresource 105 can include exact matches to most of the terms in the query109 and close matches to the remaining terms. In some implementations, aportion of text with a minimum edit distance from the query-relevanttext of the resource search tidbit relative to other portions of thetext in the resource is identified as being the closest match. In someimplementations, prefix matching can be used, such as to identify termsin the query-relevant text having the longest prefix match to terms inthe resource search tidbit. In other implementations, postfix matchingcan be used, such as to identify terms in the query-relevant text havingthe longest postfix match to terms in the resource search tidbit. Othertypes of matching can also be used, e.g., longest string matching, etc.

FIG. 10 is a flow diagram of an example process 1000 for navigating to aportion of a resource in response to selecting a resource search tidbit.As an example, the client device 106 (described with reference toFIG. 1) can perform the steps of the process 1000. More specifically,the process 1000 can be executed, for example, by computer applicationsthat are part of, our in communication with, Web browser applications orother Web search and content rendering applications running on a user'sclient device 106.

A selection environment is displayed with the rendered resource, theselection environment displaying the portion of text in the resourcethat matches the query-relevant text of the resource search tidbit(1002). For example, referring to FIG. 1, when the Web browser executingon the user's client device 106 displays the page 128 corresponding tothe resource 105, the selection environment 132 can also be displayed.Specifically, the page 128 can be a web page related to pachinko games,and the selection environment 132 can include one or more resourcesearch tidbits 134 corresponding to query-relevant text portions in theresource 105 that are related to the query terms of the query 109 (e.g.“pachinko 1975 Japan”).

In response to receiving a selection of the displayed portion of thetext, navigation occurs to the portion of the resource that includes theportion of text in the resource that matches the query-relevant text ofthe resource search tidbit (1004). For example, if the user selects aparticular resource search tidbit 134, such as one containing the tidbit“Japan sent boatloads of reconditioned pachinkos to the US in 1975,”then the user's Web browser can navigate to that portion of the resource105 that contains that text. Specifically, the Web page canautomatically scroll to the passage of interest as shown in FIG. 1 andindicated by an updated display of the page 128 and a new position ofthe scroll bars 130.

FIG. 11 is a flow diagram of an example process 1100 for performing aresource search operation using an associating of resource locators andresource search tidbits. As an example, the client device 106 (describedwith reference to FIG. 1) can perform the steps of the process 1100.More specifically, the process 1100 can be executed, for example, bycomputer applications that are part of, our in communication with, Webbrowser applications or other Web search and content renderingapplications running on a user's client device 106.

From a document object model of the search results page, the resourcesearch tidbit of the at least one search result is associated with theresource locator of the at least one search result (1102). For example,if the DOM representation of a search results page is in the form of atree of node objects, the nodes of the tree can include the associationof the resource search tidbit to a resource locator in a search result.

The association is stored in a computer memory (1104), and theassociation is accessed in the computer memory in response to aselection of a search result from the search results page (1106). Forexample, when the user selects one of the search results 111 from theWeb page 126, the Web browser executing on the user's client device 106can access the association of the resource search tidbits and the URLcorresponding to the selected search result.

The portion of text in the resource that matches the query-relevant textof the resource search tidbit associated with the resource locator ofthe at least one search result that matches the resource locator of theresource is identified (1108).

In some implementations, some of the processing described above asoccurring at the client device 106 can instead occur at the server. Forexample, the search system 110 can perform most or all of the processingneeded to determine eligibility of resource search tidbits.

In some implementations, the selection environment 132 can always bedisplayed regardless of whether the query-relevant text of the resource105 already appears on the screen.

In some implementations, in order to manage large numbers of (e.g., morethan 1 to 5) resource search tidbits (RSTs) in the selection environment132, a scroll bar can be added to allow the user to position to an RSTof interest, such as one further down the list.

In some implementations, additional tools can be added to the selectionenvironment 132, such as a tool to check off passages that have alreadybeen read. In some implementations, the user can be provided withoptions to hide selected RSTs, such a RSTs most associated with aspecific query term in which the user is no longer interested in seeingassociated RSTs. In some implementations, user options can be providedto allow the RSTs to be sorted in specific ways (e.g., by one or morequery terms). In some implementations, a search feature can be added tothe selection environment 132 that allows the user, for example, tosearch for specific text strings within the collection of RSTs.

In some implementations, automatic highlighting can occur on theportions of text in a resource that match the text of the resourcesearch tidbit, regardless of whether the resource search tidbit meets asearch operation threshold condition. For example, the text can behighlighted in light yellow upon initial display of the resource. If aselection environment is displayed, and if the user then selects the RSTassociated with the query-relevant text, the highlighting can bechanged, for example, to a strong yellow.

In some implementations, once a user is thought to have read or revieweda particular passage, highlighting can be changed to an off color, suchas by changing the initially-highlighted in yellow text to violet orsome other non-yellow highlighting color. In this way, the user can beinformed of where he or she has already been on the Web page.

Although the examples above describe providing resource search tidbitsthat include query-relevant text, other types of data can be used toidentify text for a resource search operation. For example, in someimplementations, the server system 110 can provide a byte offset andbyte length tuple that identifies the distance from the start of theresource, in bytes, of a tidbit that is of a size equal to the bytelength. Alternatively, other offset references can also be used, e.g., aparagraph number and/or sentence number. In these implementations, thematching operations at the client side can be changed accordingly.

In other implementations, the client device can request resource searchtidbits for a resource from the search system 110 asynchronously, e.g.,in response to selecting a resource from a search result. The searchsystem 110 can then perform the resource search tidbit operationsdescribed above for only that resource, and provide the identifiedresource search tidbits to the client device for processing. Thisimplementation reduces processing load on the search system 110.

Although the system above is described in the context of a server and aclient device, in some implementations, some of the server operationscan be performed on the client device. For example, when receivingsearch results, the browser application can treat the snippet as adefault resource search tidbit, and can perform the eligibilityoperations, matching operations, highlighting operations, and searchenvironment related operations described above using the snippet asinput.

Embodiments of the subject matter and the operations described in thisspecification can be implemented in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Embodiments of the subject matterdescribed in this specification can be implemented as one or morecomputer programs, i.e., one or more modules of computer programinstructions, encoded on computer storage medium for execution by, or tocontrol the operation of, data processing apparatus. Alternatively or inaddition, the program instructions can be encoded on anartificially-generated propagated signal, e.g., a machine-generatedelectrical, optical, or electromagnetic signal, that is generated toencode information for transmission to suitable receiver apparatus forexecution by a data processing apparatus. A computer storage medium canbe, or be included in, a computer-readable storage device, acomputer-readable storage substrate, a random or serial access memoryarray or device, or a combination of one or more of them. Moreover,while a computer storage medium is not a propagated signal, a computerstorage medium can be a source or destination of computer programinstructions encoded in an artificially-generated propagated signal. Thecomputer storage medium can also be, or be included in, one or moreseparate physical components or media (e.g., multiple CDs, disks, orother storage devices).

The operations described in this specification can be implemented asoperations performed by a data processing apparatus on data stored onone or more computer-readable storage devices or received from othersources.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includespecial purpose logic circuitry, e.g., an FPGA (field programmable gatearray) or an ASIC (application-specific integrated circuit). Theapparatus can also include, in addition to hardware, code that createsan execution environment for the computer program in question, e.g.,code that constitutes processor firmware, a protocol stack, a databasemanagement system, an operating system, a cross-platform runtimeenvironment, a virtual machine, or a combination of one or more of them.The apparatus and execution environment can realize various differentcomputing model infrastructures, such as web services, distributedcomputing and grid computing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor data (e.g., one or more scripts stored in a markup languagedocument), in a single file dedicated to the program in question, or inmultiple coordinated files (e.g., files that store one or more modules,sub-programs, or portions of code). A computer program can be deployedto be executed on one computer or on multiple computers that are locatedat one site or distributed across multiple sites and interconnected by acommunication network.

The processes and logic flows described in this specification can beperformed by one or more programmable processors executing one or morecomputer programs to perform actions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application-specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data, e.g., magnetic, magneto-optical disks, or optical disks.However, a computer need not have such devices. Moreover, a computer canbe embedded in another device, e.g., a mobile telephone, a personaldigital assistant (PDA), a mobile audio or video player, a game console,a Global Positioning System (GPS) receiver, or a portable storage device(e.g., a universal serial bus (USB) flash drive), to name just a few.Devices suitable for storing computer program instructions and datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube) or LCD (liquidcrystal display) monitor, for displaying information to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back-end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an implementation of the subjectmatter described in this specification, or any combination of one ormore such back-end, middleware, or front-end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include a local area network (“LAN”) and a widearea network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits data (e.g., an HTML page) to a clientdevice (e.g., for purposes of displaying data to and receiving userinput from a user interacting with the client device). Data generated atthe client device (e.g., a result of the user interaction) can bereceived from the client device at the server.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable subcombination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous.

1. A computer-implemented method performed by data processing apparatus,the method comprising: receiving a query, the query including one ormore query terms; receiving, for each of a plurality of resourcesidentified as being relevant to the query, one or more tidbits, eachtidbit being query-relevant text extracted from the resource; for eachtidbit extracted from each resource: determining whether the tidbit iseligible for a resource search operation that occurs in response to theresource being rendered on a client device; and in response todetermining that the tidbit is eligible for a resource search operation,marking the tidbit as being a resource search tidbit; and providing, foreach of the plurality of resources, a corresponding search resultresponsive to the query, each search result including a resource locatorthat specifies the location of the resource, and wherein at least onesearch result includes a resource search tidbit.
 2. The method of claim1, wherein: each search result includes a snippet, the snippet beingquery-relevant text extracted from the resource specified by theresource locator of the search result, and the snippet is rendered onthe client device as part of the search result; and the query-relevanttext of the resource search tidbit included in the search result is asubset of the query-relevant text of the snippet included in the searchresult.
 3. The method of claim 1, wherein: each search result includes asnippet, the snippet being query-relevant text extracted from theresource specified by the resource locator of the search result, and thesnippet is rendered on the client device as part of the search result;the query-relevant text of the resource search tidbit included in thesearch result is independent of the query-relevant text of the snippetincluded in the search result; and the resource search tidbit is notrendered on the client device as part of the search result.
 4. Themethod of claim 1, wherein determining whether the tidbit is eligiblefor a resource search operation that occurs in response to the resourcebeing rendered on a client device comprises: identifying query terms ina title section of the resource; identifying query terms in the tidbit;and determining that the tidbit is eligible for the resource searchoperation if there is at least one query term identified in the tidbitthat is not identified in the title section of the resource.
 5. Themethod of claim 4, wherein: identifying query terms in a title sectionof the resource comprises identifying query terms in the title sectionof the resources and synonyms of the query terms identified in the titlesection; identifying query terms in the tidbit comprises identifyingquery terms in the tidbit and synonyms of the query terms in the tidbitas identified query terms; and determining that the tidbit is eligiblefor the resource search operation comprises determining that the tidbitis eligible for the resource search operation if there is at least oneidentified query term in the tidbit that is not identified in the titlesection of the resource.
 6. The method of claim 1, wherein determiningwhether the tidbit is eligible for a resource search operation thatoccurs in response to the resource being rendered on a client devicecomprises: identifying query terms in a title section of the resourceand the resource locator specifying the location of the resource;identifying query terms in the tidbit; and determining that the tidbitis eligible for the resource search operation if there is at least onequery term identified in the tidbit that is not identified in either ofthe title section of the resource and the resource locator specifyingthe location of the resource.
 7. The method of claim 1, whereindetermining whether the tidbit is eligible for a resource searchoperation that occurs in response to the resource being rendered on aclient device comprises determining that the tidbit is eligible for theresource search operation if all of the query terms are included in thetidbit.
 8. The method of claim 1, wherein the query-relevant text ofeach tidbit is a contiguous portion of text extracted from the resource.9. A computer-implemented method performed by a client device, themethod comprising: receiving, in response to a query including one ormore query terms, a search results page including search resultsresponsive to the query, each search result including a resource locatorthat specifies the location of a resource identified as being relevantto the query, and wherein at least one search result includes a resourcesearch tidbit, the resource search tidbit being query-relevant textextracted from the resource and eligible for a research search operationin response to the resource specified by the resource locator of the atleast one search result being rendered on the client device; receiving aselection of the at least one search result at the client device;receiving, in response to the selection, the resource specified by theresource locator of the at least one search result; rendering theresource at the client device; identifying a portion of text in theresource that matches the query-relevant text of the resource searchtidbit; and performing the resource search operation only if theidentified portion of the text matching the query-relevant text of theresource search tidbit meets a search operation threshold condition. 10.The method of claim 9, wherein performing the resource search operationonly if the identified portion of the text matching the query-relevanttext of the resource search tidbit meets a search operation thresholdcondition comprises performing the search operation only if thequery-relevant text of the resource search tidbit is not within aviewport of the client device when the resource is initially rendered onthe client device.
 11. The method of claim 9, wherein performing theresource search operation only if the identified portion of the textmatching the query-relevant text of the resource search tidbit meets asearch operation threshold condition comprises performing the searchoperation only if the query-relevant text of the resource search tidbitis displayed at a location that exceeds a maximum display location. 12.The method of claim 11, wherein the maximum display location is amaximum pixel location.
 13. The method of claim 9, wherein identifying aportion of text in the resource that matches the query-relevant text ofthe resource search tidbit comprises: searching for a portion of text inthe resource that exactly matches the query-relevant text of theresource search tidbit; if a portion of text in the resource thatexactly matches the query-relevant text of the resource search tidbit isfound from the search, identifying the portion of text as matching thequery-relevant text of the resource search tidbit; and if no portion oftext in the resource that exactly matches the query-relevant text of theresource search tidbit is found from the search, identifying a portionof text in the resource that most closely matches the query-relevanttext of the resource tidbit as matching the query-relevant text of theresource search tidbit.
 14. The method of claim 13, wherein identifyingthe portion of text in the resource that most closely matches thequery-relevant text of the resource tidbit comprises identifying theportion of the text in the resource that has a minimum edit distancefrom the query-relevant text of the resource search tidbit relative toother portions of the text in the resource.
 15. The method of claim 9,wherein each resource search tidbit includes at least one query termthat is not included in a title section of the resource.
 16. The methodof claim 9, wherein each resource search tidbit includes at least onequery term that is not included in either of a title section of theresource and the resource locator specifying the location of theresource.
 17. The method of claim 9, wherein performing the resourcesearch operation comprises: displaying a selection environment with therendered resource, the selection environment displaying the portion oftext in the resource that matches the query-relevant text of theresource search tidbit; and in response to receiving a selection of thedisplayed portion of the text, navigating to the portion of the resourcethat includes the portion of text in the resource that matches thequery-relevant text of the resource search tidbit.
 18. The method ofclaim 9, further comprising automatically highlighting the portion oftext in the resource that matches the query-relevant text of theresource search tidbit in response to navigating to the portion of thetext.
 19. The method of claim 9, further comprising automaticallyhighlighting the portion of text in the resource that matches thequery-relevant text of the resource search tidbit only if the identifiedportion of the text meets the search operation threshold condition. 20.The method of claim 9, further comprising: associating, from a documentobject model of the search results page, the resource search tidbit ofthe at least one search result with the resource locator of the at leastone search result; storing the association in a computer memory; andaccessing the association in the computer memory in response to aselection of a search result from the search results page; whereinidentifying the portion of text in the resource that matches thequery-relevant text of the resource search tidbit comprises identifyingthe portion of text in the resource that matches the query-relevant textof the resource search tidbit associated with the resource locator ofthe at least one search result that matches the resource locator of theresource.
 21. The method of claim 9, wherein: each search resultincludes a snippet, the snippet being query-relevant text extracted fromthe resource specified by the resource locator of the search result, andthe snippet is rendered on the client device as part of the searchresult; and the query-relevant text of the resource search tidbitincluded in the at least one search result is a subset of thequery-relevant text of the snippet included in the at least one searchresult.
 22. The method of claim 9, wherein: each search result includesa snippet, the snippet being query-relevant text extracted from theresource specified by the resource locator of the search result, and thesnippet is rendered on the client device as part of the search result;the query-relevant text of the resource search tidbit included in the atleast one search result is independent of the query-relevant text of thesnippet included in the at least one search result; and the resourcesearch tidbit is not rendered on the client device as part of the atleast one search result.
 23. A system, comprising: a data processingapparatus; and a data store in data communication with the dataprocessing apparatus and storing instructions executable by a dataprocessing apparatus and that upon execution cause the data processingapparatus to perform operations comprising: receiving a query, the queryincluding one or more query terms; receiving, for each of a plurality ofresources identified as being relevant to the query, one or moretidbits, each tidbit being query-relevant text extracted from theresource; for each tidbit extracted from each resource: determiningwhether the tidbit is eligible for a resource search operation thatoccurs in response to the resource being rendered on a client device;and in response to determining that the tidbit is eligible for aresource search operation, marking the tidbit as being a resource searchtidbit; and providing, for each of the plurality of resources, acorresponding search result responsive to the query, each search resultincluding a resource locator that specifies the location of theresource, and wherein at least one search result includes a resourcesearch tidbit.
 24. A system, comprising: a data processing apparatus;and a data store in data communication with the data processingapparatus and storing instructions executable by a data processingapparatus and that upon execution cause the data processing apparatus toperform operations comprising: receiving, in response to a queryincluding one or more query terms, a search results page includingsearch results responsive to the query, each search result including aresource locator that specifies the location of a resource identified asbeing relevant to the query, and wherein at least one search resultincludes a resource search tidbit, the resource search tidbit beingquery-relevant text extracted from the resource and eligible for aresearch search operation in response to the resource specified by theresource locator of the at least one search result being rendered on theclient device; receiving a selection of the at least one search resultat the client device; receiving, in response to the selection, theresource specified by the resource locator of the at least one searchresult; rendering the resource at the client device; identifying aportion of text in the resource that matches the query-relevant text ofthe resource search tidbit; and performing the resource search operationonly if the identified portion of the text matching the query-relevanttext of the resource search tidbit meets a search operation thresholdcondition.
 25. Software stored on a computer readable computer storagedevice and comprising instructions executable by a data processingapparatus and that upon execution cause the data processing apparatus toperform operations comprising: receiving, in response to a queryincluding one or more query terms, a search results page includingsearch results responsive to the query, each search result including aresource locator that specifies the location of a resource identified asbeing relevant to the query, and wherein at least one search resultincludes a resource search tidbit, the resource search tidbit beingquery-relevant text extracted from the resource and eligible for aresearch search operation in response to the resource specified by theresource locator of the at least one search result being rendered on theclient device; receiving a selection of the at least one search resultat the client device; receiving, in response to the selection, theresource specified by the resource locator of the at least one searchresult; rendering the resource at the client device; identifying aportion of text in the resource that matches the query-relevant text ofthe resource search tidbit; and performing the resource search operationonly if the identified portion of the text matching the query-relevanttext of the resource search tidbit meets a search operation thresholdcondition.